before:

after (outdated, see below):

Arguably "CLICK HERE" in caps is not the nicest thing, but I didn't have an idea how to improve it otherwise.
One thing could be to color links in blue boxes something other than blue in general.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.11%. Comparing base (87a4d34) to head (f016c7b).
Report is 2 commits behind head on master.

@@           Coverage Diff           @@
##           master    #6588   +/-   ##
=======================================
  Coverage   99.11%   99.11%           
=======================================
  Files         399      399           
  Lines       40717    40717           
=======================================
  Hits        40358    40358           
  Misses        359      359           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Arguably "CLICK HERE" in caps is not the nicest thing, but I didn't have an idea how to improve it otherwise.

I had the same though. Considering we can render an a element here we can probably also render a button with the text "Clone". So I would do that. Maybe you can actually keep using an a element and just add class="btn btn-primary".

Arguably "CLICK HERE" in caps is not the nicest thing, but I didn't have an idea how to improve it otherwise.

I had the same though. Considering we can render an a element here we can probably also render a button with the text "Clone". So I would do that. Maybe you can actually keep using an a element and just add class="btn btn-primary".

A button, excellent!
Done that

Maybe "example distribution" could now be a link to GitHub. This way users who want to know more before hitting the "Clone" button could have a look beforehand. Otherwise it is actually still quite unclear what exactly will be cloned.

@okurz I think your questions lead to far for a PR that is merely attempting to improve the UI (and not the logic behind). So I wouldn't block the merging of this PR on this discussion.

… when openQA should clone the test distribution automatically on start?

On the start of what? I don't think it is desirable that any openQA deployment automatically/unasked clones some additional repository from GitHub on first launch (if you mean that). We could trigger this automatically when one enters the specific page, though. I personally find it better if the cloning is triggered semi-automatic so users can follow better what's going on and the context of a potential error showing up is clearer.

Under which circumstances do we get here?

By clicking on "Create … Example tests" on a freshly installed openQA instance where our example distribution hasn't been cloned yet. It is required to load the scenario definitions from there.

… when openQA should clone the test distribution automatically on start?

On the start of what? I don't think it is desirable that any openQA deployment automatically/unasked clones some additional repository from GitHub on first launch (if you mean that). We could trigger this automatically when one enters the specific page, though. I personally find it better if the cloning is triggered semi-automatic so users can follow better what's going on and the context of a potential error showing up is clearer.

Under which circumstances do we get here?

By clicking on "Create … Example tests" on a freshly installed openQA instance where our example distribution hasn't been cloned yet. It is required to load the scenario definitions from there.

I see. The document is expanded. How about a button inside the scenario definitions text edit field to load the file (not the complete repo) remotely on demand? Like "Click here to fetch example scenario definitions"

I now changed the text to be more informative.
It's needed to automatically fill out all form fields (as you can see in my first screenshots, version, flavor and architecture are empty initially).
I don't want to spend more time on this right now, so for adding a button inside a text area I think there should be a ticket.